Description:

Adds regression coverage for swc compile --watch --out-file, matching the Windows scenario reported in #10524.

The new CLI test starts watch mode with a single output file, waits for the initial output, rewrites the input file, and asserts that the rebuilt output:

• drops stale content from the first build
• contains only one console.log
• is overwritten instead of appended/prepended

This locks in the current rebuild behavior for single-file watch output.

This also bumps two Cargo.lock entries to clear current cargo-deny advisories reported by CI:

• anyhow from 1.0.100 to 1.0.103
• crossbeam-epoch from 0.9.18 to 0.9.20

Verified with:

• cargo test -p swc_cli_impl issue_10524_watch_out_file_overwrites_rebuilt_output -- --nocapture
• cargo-deny 0.18.9 check
• manual Windows watch repro using target/debug/swc.exe compile src/app/v1/simple.js --out-file public/v1/output.js --watch; after rewriting the input, output.js contained only console.log("Hello, world 2!!");
• cargo fmt -p swc_cli_impl --check
• cargo clippy -p swc_cli_impl --tests -- -D warnings

I also tried broader local checks on Windows:

• cargo fmt --all --check failed before formatting with os error 206 (path too long)
• cargo test -p swc_cli_impl -- --nocapture ran the new test successfully, but the full suite has existing Windows failures unrelated to this change, including issue_8265_1/issue_8667_1 using unavailable ls, plus existing path/root-mode/watch-dir failures

BREAKING CHANGE:

None.

Related issue (if exists):

Closes #10524